Sharing electronic file metadata in a networked computing environment

ABSTRACT

Embodiments of the present invention provide an approach for sharing electronic file metadata in a networked computing environment (e.g., a cloud computing environment). In a typical embodiment, metadata related to electronic files stored in a shared storage device is maintained and updated. Such metadata may be viewable via a user interface of one or more applications used to access the files (e.g., from a plurality of computerized/electronic devices). Among other things, the metadata may identify previous accesses of the files (e.g., by user, date/time, etc.), and may be provided in a list or the like.

TECHNICAL FIELD

In general, embodiments of the present invention relate to electronicfile metadata. Specifically, embodiments of the present invention relateto the sharing of electronic file metadata in a networked computingenvironment (e.g., a cloud computing environment).

BACKGROUND

The networked computing environment (e.g., cloud computing environment)is an enhancement to the predecessor grid environment, whereby multiplegrids and other computation resources may be further enhanced by one ormore additional abstraction layers (e.g., a cloud layer), thus makingdisparate devices appear to an end-consumer as a single pool of seamlessresources. These resources may include such things as physical orlogical computing engines, servers and devices, device memory, andstorage devices, among others.

In cloud computing and shared file systems, users may store files in astorage location from which the files may be accessed using variouscomputers and/or devices. Challenges may exist, however, in providingcurrent metadata for such files in a shared environment. Such challengesmay be complicated as the size of a given directory or folder grows,thus making it more difficult to efficiently locate desired files orreadily obtain pertinent information about such files.

SUMMARY

Embodiments of the present invention provide an approach for sharingelectronic file metadata in a networked computing environment (e.g., acloud computing environment). In a typical embodiment, metadata relatedto electronic files stored in a shared storage device is maintained andupdated. Such metadata may be viewable via a user interface of one ormore applications used to access the files (e.g., from a plurality ofcomputerized/electronic devices). Among other things, the metadata mayidentify previous accessing of the files (e.g., by user, date/time,etc.), and may be provided in a list or the like.

A first aspect of the present invention provides a computer-implementedmethod for sharing file metadata in a networked computing environment,comprising: detecting access to an electronic file stored in a sharedstorage device of the networked computing environment; updating a set ofmetadata associated with the electronic file to reflect the access tothe electronic file; storing the updated set of metadata in the sharedstorage device and associating the updated set of metadata with theelectronic file; and providing access to the updated set of metadata viaan application utilized to access the electronic file.

A second aspect of the present invention provides a system for sharingfile metadata in a networked computing environment, comprising: a memorymedium comprising instructions; a bus coupled to the memory medium; anda processor coupled to the bus that when executing the instructionscauses the system to: detect access to an electronic file stored in ashared storage device of the networked computing environment; update aset of metadata associated with the electronic file to reflect theaccess to the electronic file; store the updated set of metadata in theshared storage device and associate the updated set of metadata with theelectronic file; and provide access to the updated set of metadata viaan application utilized to access the electronic file.

A third aspect of the present invention provides a computer programproduct for sharing file metadata in a networked computing environment,the computer program product comprising a computer readable storagemedia, and program instructions stored on the computer readable storagemedia, to: detect access to an electronic file stored in a sharedstorage device of the networked computing environment; update a set ofmetadata associated with the electronic file to reflect the access tothe electronic file; store the updated set of metadata in the sharedstorage device and associate the updated set of metadata with theelectronic file; and provide access to the updated set of metadata viaan application utilized to access the electronic file.

A fourth aspect of the present invention provides a method for deployinga system for sharing file metadata in a networked computing environment:providing a computer infrastructure being operable to: detect access toan electronic file stored in a shared storage device of the networkedcomputing environment; update a set of metadata associated with theelectronic file to reflect the access to the electronic file; store theupdated set of metadata in the shared storage device and associate theupdated set of metadata with the electronic file; and provide access tothe updated set of metadata via an application utilized to access theelectronic file.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readilyunderstood from the following detailed description of the variousaspects of the invention taken in conjunction with the accompanyingdrawings in which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 depicts a system diagram according to an embodiment of thepresent invention.

FIG. 5 depicts a process flow diagram according to an embodiment of thepresent invention.

FIG. 6 depicts another process flow diagram according to an embodimentof the present invention.

FIG. 7 depicts a process flow diagram according to an embodiment of thepresent invention.

FIG. 8 depicts a method flow diagram according to an embodiment of thepresent invention

The drawings are not necessarily to scale. The drawings are merelyschematic representations, not intended to portray specific parametersof the invention. The drawings are intended to depict only typicalembodiments of the invention, and therefore should not be considered aslimiting the scope of the invention. In the drawings, like numberingrepresents like elements.

DETAILED DESCRIPTION

Illustrative embodiments will now be described more fully herein withreference to the accompanying drawings, in which embodiments are shown.This disclosure may, however, be embodied in many different forms andshould not be construed as limited to the embodiments set forth herein.Rather, these embodiments are provided so that this disclosure will bethorough and complete and will fully convey the scope of this disclosureto those skilled in the art. In the description, details of well-knownfeatures and techniques may be omitted to avoid unnecessarily obscuringthe presented embodiments.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of this disclosure.As used herein, the singular forms “a”, “an”, and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Furthermore, the use of the terms “a”, “an”, etc., do notdenote a limitation of quantity, but rather denote the presence of atleast one of the referenced items. The term “set” is intended to mean aquantity of at least one. It will be further understood that the terms“comprises” and/or “comprising”, or “includes” and/or “including”, whenused in this specification, specify the presence of stated features,regions, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,regions, integers, steps, operations, elements, components, and/orgroups thereof.

Embodiments of the present invention provide an approach for sharingelectronic file metadata in a networked computing environment (e.g., acloud computing environment). In a typical embodiment, metadata relatedto electronic files stored in a shared storage device is maintained andupdated. Such metadata may be viewable via a user interface of one ormore applications used to access the files (e.g., from a plurality ofcomputerized/electronic devices). Among other things, the metadata mayidentify previous accessing of the files (e.g., by user, date/time,etc.), and may be provided in a list or the like.

It is understood in advance that although this disclosure includes adetailed description of cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded, automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active consumer accounts). Resource usage canbe monitored, controlled, and reported providing transparency for boththe provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited consumer-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication-hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10, there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM, or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

The embodiments of the invention may be implemented as a computerreadable signal medium, which may include a propagated data signal withcomputer readable program code embodied therein (e.g., in baseband or aspart of a carrier wave). Such a propagated signal may take any of avariety of forms including, but not limited to, electro-magnetic,optical, or any suitable combination thereof. A computer readable signalmedium may be any computer readable medium that is not a computerreadable storage medium and that can communicate, propagate, ortransport a program for use by or in connection with an instructionexecution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium including, but not limited to, wireless,wireline, optical fiber cable, radio-frequency (RF), etc., or anysuitable combination of the foregoing.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation. Memory28 may also have an operating system, one or more application programs,other program modules, and program data. Each of the operating system,one or more application programs, other program modules, and programdata or some combination thereof, may include an implementation of anetworking environment. Program modules 42 generally carry out thefunctions and/or methodologies of embodiments of the invention asdescribed herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a consumer to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as private, community,public, or hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms, and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes. In oneexample, IBM® zSeries® systems and RISC (Reduced Instruction SetComputer) architecture based servers. In one example, IBM pSeries®systems, IBM System x® servers, IBM BladeCenter® systems, storagedevices, networks, and networking components. Examples of softwarecomponents include network application server software. In one example,IBM WebSphere® application server software and database software. In oneexample, IBM DB2® database software. (IBM, zSeries, pSeries, System x,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide.)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.Consumer portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provides pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA. Further shown in management layer is metadatasharing, which represents the functionality that is provided under theembodiments of the present invention.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and consumer data storage and backup. As mentioned above,all of the foregoing examples described with respect to FIG. 3 areillustrative only, and the invention is not limited to these examples.

It is understood that all functions of the present invention asdescribed herein typically may be performed by the metadata sharingfunctionality (of management layer 64, which can be tangibly embodied asmodules of program code 42 of program/utility 40 (FIG. 1). However, thisneed not be the case. Rather, the functionality recited herein could becarried out/implemented and/or enabled by any of the layers 60-66 shownin FIG. 3.

It is reiterated that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather, theembodiments of the present invention are intended to be implemented withany type of networked computing environment now known or laterdeveloped.

Referring now to FIG. 4, a system diagram describing the functionalitydiscussed herein according to an embodiment of the present invention isshown. It is understood that the teachings recited herein may bepracticed within any type of networked computing environment 86 (e.g., acloud computing environment 50). A computer system/server 12, which canbe implemented as either a stand-alone computer system or as a networkedcomputer system is shown in FIG. 4. In the event the teachings recitedherein are practiced in a networked computing environment 86, eachclient need not have a metadata sharing engine (engine 70). Rather,engine 70 could be loaded on a server or server-capable device thatcommunicates (e.g., wirelessly) with the clients to provide metadatasharing therefor. Regardless, as depicted, engine 70 is shown withincomputer system/server 12. In general, engine 70 can be implemented asprogram/utility 40 on computer system 12 of FIG. 1 and can enable thefunctions recited herein. As further shown, engine 70 (in oneembodiment) comprises a rules and/or computational engine that processesa set (at least one) of rules/logic 72 and/or provides metadata sharinghereunder.

Along these lines, engine 70 may perform multiple functions similar to ageneral-purpose computer. Specifically, among other functions, engine 70may (among other things): detect access to an electronic file 82A-Nstored in a shared storage device 80 of the networked computingenvironment 86 (e.g., via an application 74 on a computerized device 76operated by a user 78); update a set of metadata 84A-N associated withthe electronic file 82A-N to reflect the access to the electronic file82A-N; store the updated set of metadata 84A-N in the shared storagedevice 80 and associating the updated set of metadata 84A-N with theelectronic file 82A-N; provide access to the updated set of metadata84A-N via an application 74 utilized to access the electronic file 82A-N(e.g., from one or more computerized devices such as computerized device76); and/or display the updated set of metadata 84A-N via a userinterface associated with the application (e.g., a list of recentlyaccessed electronic files 82A-N in the shared storage device 80. Thelist may identify the electronic file 82A-N, a user accessing theelectronic file 82A-N, a date/time the electronic file 82A-N was lastaccessed, etc.

In general, these concepts may be implemented using the followingimplementation:

-   -   1. An application (e.g., a text editor, a text viewer, tools        application, etc.) opens a file which could be in a shared        storage device/location (e.g., a cloud storage device).    -   2. The application maintains a list of the recently        used/accessed files.    -   3. When the list is updated with metadata to reflect the current        use of the file, the system may publish the list to the shared        storage device (shared storage, cloud storage, etc.) where other        devices can also access the file and/or list.    -   4. A user logs into a computerized device that has access to the        same shared storage device and/or file.    -   5. The user opens the application, which reads the metadata of        the list of recently used files.    -   6. The application may then retrieve a selected file from the        shared storage device.

It is understood that the metadata created and/or updated hereunder neednot be limited to a recent file list. Rather, metadata may include anytype of metadata that an application can maintain. Moreover, if acloud-based storage mechanism is shared across a group of individuals,an identity of the last user to modify a given file could be shown nextto the file in the recent file list. Alternatively, a user may set apreference to only view those files in which the user was the last toedit.

Illustrative Example

FIGS. 5-7 depict the above teachings in accordance with an illustrativeexample. It is understood in advance, however, that these teachingsdemonstrated in FIGS. 5-7 are illustrative only and that similarteachings may be applied to other implementations hereunder.

As shown in FIG. 5, a user 100 connects to a machine/computerized device102 and uses an application (e.g., text editor 104) to work on one ormore files 108A-C that are located in a cloud storage system 106. Whenthe application initiates, or has an update of metadata, the applicationmay “push” a corresponding metadata file 110 to cloud storage system 106as well.

Referring now to FIG. 6, assume that user 100 logs into a differentcomputing device 102B (as opposed to computing device 102A) that has thesame application 104B (as opposed to 104A) and also access to files108A-C stored in cloud storage system 102. Under the teachings recitedherein, user 100 may access metadata file 110 regardless of which devicehe/she utilized. Moreover, the system herein may represent metadata file110 graphically in a list displayed via the user interface correspondingto application 104.

Referring to FIG. 7, an illustrative user interface 200 according to anembodiment of the present invention is shown. As shown, interface 200may include a list 202 as generated by engine 70 (FIG. 4). The list mayinclude local files 204 and/or shared files 206. List 202 may beaugmented with other metadata such as which users have most recentlyaccessed the files, the date/time of last access, the geographiclocation from which the files were last accessed, etc.

Referring now to FIG. 8, a method flow diagram according to anembodiment of the present invention is shown. As depicted, in step S1,access to an electronic file stored in a shared storage device of thenetworked computing environment is detected. In step S2, a set ofmetadata associated with the electronic file is updated to reflect theaccess to the electronic file. In step S3, the updated set of metadatais stored in the shared storage device and associates the updated set ofmetadata with the electronic file. In step S4, access to the updated setof metadata is provided via an application (e.g., via a list displayedvia a user interface of the application) utilized to access theelectronic file.

While shown and described herein as a metadata sharing solution, it isunderstood that the invention further provides various alternativeembodiments. For example, in one embodiment, the invention provides acomputer-readable/useable medium that includes computer program code toenable a computer infrastructure to provide metadata sharingfunctionality as discussed herein. To this extent, thecomputer-readable/useable medium includes program code that implementseach of the various processes of the invention. It is understood thatthe terms computer-readable medium or computer-useable medium compriseone or more of any type of physical embodiment of the program code. Inparticular, the computer-readable/useable medium can comprise programcode embodied on one or more portable storage articles of manufacture(e.g., a compact disc, a magnetic disk, a tape, etc.), on one or moredata storage portions of a computing device, such as memory 28 (FIG. 1)and/or storage system 34 (FIG. 1) (e.g., a fixed disk, a read-onlymemory, a random access memory, a cache memory, etc.).

In another embodiment, the invention provides a method that performs theprocess of the invention on a subscription, advertising, and/or feebasis. That is, a service provider, such as a Solution Integrator, couldoffer to provide metadata sharing functionality. In this case, theservice provider can create, maintain, support, etc., a computerinfrastructure, such as computer system 12 (FIG. 1) that performs theprocesses of the invention for one or more consumers. In return, theservice provider can receive payment from the consumer(s) under asubscription and/or fee agreement and/or the service provider canreceive payment from the sale of advertising content to one or morethird parties.

In still another embodiment, the invention provides acomputer-implemented method for metadata sharing. In this case, acomputer infrastructure, such as computer system 12 (FIG. 1), can beprovided and one or more systems for performing the processes of theinvention can be obtained (e.g., created, purchased, used, modified,etc.) and deployed to the computer infrastructure. To this extent, thedeployment of a system can comprise one or more of: (1) installingprogram code on a computing device, such as computer system 12 (FIG. 1),from a computer-readable medium; (2) adding one or more computingdevices to the computer infrastructure; and (3) incorporating and/ormodifying one or more existing systems of the computer infrastructure toenable the computer infrastructure to perform the processes of theinvention.

As used herein, it is understood that the terms “program code” and“computer program code” are synonymous and mean any expression, in anylanguage, code, or notation, of a set of instructions intended to causea computing device having an information processing capability toperform a particular function either directly or after either or both ofthe following: (a) conversion to another language, code, or notation;and/or (b) reproduction in a different material form. To this extent,program code can be embodied as one or more of: an application/softwareprogram, component software/a library of functions, an operating system,a basic device system/driver for a particular computing device, and thelike.

A data processing system suitable for storing and/or executing programcode can be provided hereunder and can include at least one processorcommunicatively coupled, directly or indirectly, to memory elementsthrough a system bus. The memory elements can include, but are notlimited to, local memory employed during actual execution of the programcode, bulk storage, and cache memories that provide temporary storage ofat least some program code in order to reduce the number of times codemust be retrieved from bulk storage during execution. Input/outputand/or other external devices (including, but not limited to, keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening device controllers.

Network adapters also may be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems,remote printers, storage devices, and/or the like, through anycombination of intervening private or public networks. Illustrativenetwork adapters include, but are not limited to, modems, cable modems,and Ethernet cards.

The foregoing description of various aspects of the invention has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formdisclosed and, obviously, many modifications and variations arepossible. Such modifications and variations that may be apparent to aperson skilled in the art are intended to be included within the scopeof the invention as defined by the accompanying claims.

What is claimed is:
 1. A computer-implemented method for sharing filemetadata in a networked computing environment, comprising: detecting anopening of an electronic file while the electronic file is being storedin a cloud-based shared storage device of the networked computingenvironment, the networked computing environment comprising a cloudcomputing environment, and the shared storage device comprising a cloudstorage device; updating a set of metadata associated with theelectronic file to reflect the opening of the electronic file; storingthe updated set of metadata in the shared storage device and associatingthe updated set of metadata with the electronic file; and providingaccess to the updated set of metadata via an application utilized toaccess the electronic file, the providing comprising displaying theupdated set of metadata via a user interface associated with theapplication.
 2. The computer-implemented method of claim 1, the openingbeing attempted from a first computerized device.
 3. Thecomputer-implemented method of claim 2, further comprising accessing theupdated set of metadata from a second computerized device.
 4. Thecomputer-implemented method of claim 1, the updated set of metadatabeing represented as a list of recently accessed electronic files in theshared storage device, the list identifying the electronic file.
 5. Thecomputer-implemented method of claim 4, the updated set of metadataidentifying a user to last access the electronic file.
 6. A system forsharing file metadata in a networked computing environment, comprising:a memory device comprising instructions; a bus coupled to the memorydevice; and a processor coupled to the bus that when executing theinstructions causes the system to: detect an opening of an electronicfile while the electronic file is being stored in a cloud-based sharedstorage device of the networked computing environment, the networkedcomputing environment comprising a cloud computing environment, and theshared storage device comprising a cloud storage device; update a set ofmetadata associated with the electronic file to reflect the opening ofthe electronic file; store the updated set of metadata in the sharedstorage device and associate the updated set of metadata with theelectronic file; and provide access to the updated set of metadata viaan application utilized to access the electronic file, the providingcomprising displaying the updated set of metadata via a user interfaceassociated with the application.
 7. The system of claim 6, the openingbeing attempted from a first computerized device.
 8. The system of claim7, the memory device further comprising instructions for causing thesystem to access the updated set of metadata from a second computerizeddevice.
 9. The system of claim 6, the updated set of metadata beingrepresented as a list of recently accessed electronic files in theshared storage device, the list identifying the electronic file.
 10. Thesystem of claim 9, the updated set of metadata identifying a user tolast access the electronic file.
 11. A computer program product forsharing file metadata in a networked computing environment, the computerprogram product comprising a computer readable hardware storage device,and program instructions stored on the computer readable hardwarestorage device, to: detect an opening of an electronic file while theelectronic file is being stored in a cloud-based shared storage deviceof the networked computing environment, the networked computingenvironment comprising a cloud computing environment, and the sharedstorage device comprising a cloud storage device; update a set ofmetadata associated with the electronic file to reflect the opening ofthe electronic file; store the updated set of metadata in the sharedstorage device and associate the updated set of metadata with theelectronic file; and provide access to the updated set of metadata viaan application utilized to access the electronic file, the providingcomprising displaying the updated set of metadata via a user interfaceassociated with the application.
 12. The computer program product ofclaim 11, the opening being attempted from a first computerized device.13. The computer program product of claim 12, the computer readablehardware storage device further comprising instructions to access theupdated set of metadata from a second computerized device.
 14. Thecomputer program product of claim 11, the updated set of metadata beingrepresented as a list of recently accessed electronic files in theshared storage device, the list identifying the electronic file.
 15. Thecomputer program product of claim 14, the updated set of metadataidentifying a user to last access the electronic file.
 16. A method fordeploying a system for sharing file metadata in a networked computingenvironment, comprising: providing a computer infrastructure beingoperable to: detect an opening of an electronic file while theelectronic file is being stored in a cloud-based shared hardware storagedevice of the networked computing environment, the networked computingenvironment comprising a cloud computing environment, and the sharedstorage device comprising a cloud storage device; update a set ofmetadata associated with the electronic file to reflect the opening ofthe electronic file; store the updated set of metadata in the sharedstorage device and associate the updated set of metadata with theelectronic file; and provide access to the updated set of metadata viaan application utilized to access the electronic file, the providingcomprising displaying the updated set of metadata via a user interfaceassociated with the application.